System and method for grouping and assigning channels in a network system

ABSTRACT

System and methods are provided for dynamically assigning wireless channels to priority groups based on characteristics of the channels, the environment in which the channels will be used, regulatory requirements, and/or capabilities of client devices. Thereafter, channels may be intelligently assigned to access points to achieve one or more goals. For example, wireless channels may be assigned to access points to ensure balanced coverage throughout the network system for client devices of each type/capability, to minimize effects of wireless interference in the network system, to increase fault tolerance in the network system, and/or to generally improve the coverage and quality of connections in the network system.

TECHNICAL FIELD

The present disclosure relates to dynamically categorizing wirelesschannels based on priorities and assigning channels to access points toensure well-balanced, wide coverage, of stable channels in a networksystem.

BACKGROUND

Over the last decade, there has been a substantial increase in the useand deployment of wireless client devices, from dual-mode smartphones totablets capable of operating in accordance with a particular Instituteof Electrical and Electronics Engineers (IEEE) standard. With “wireless”becoming the de-facto medium for connectivity among users, it has becomeincreasingly important for network systems to intelligently manageconnections.

In some systems, multiple access points may be used to cover aparticular area. Each of these access points may operate using separatewireless channels. However, in these traditional systems assignment ofchannels is performed based on the assumption that each channel isequal. This assumption may result in a network system that fails toadequately support particular client devices and/or provides poornetwork coverage.

The approaches described in this section are approaches that could bepursued, but not necessarily approaches that have been previouslyconceived or pursued. Therefore, unless otherwise indicated, it shouldnot be assumed that any of the approaches described in this sectionqualify as prior art merely by virtue of their inclusion in thissection.

BRIEF DESCRIPTION OF THE DRAWINGS

The embodiments are illustrated by way of example and not by way oflimitation in the figures of the accompanying drawings in which likereferences indicate similar elements. It should be noted that referencesto “an” or “one” embodiment in this disclosure are not necessarily tothe same embodiment, and they mean at least one. In the drawings:

FIG. 1 shows a block diagram example of a network system in accordancewith one or more embodiments;

FIG. 2 shows a block diagram example of an access point in accordancewith one or more embodiments;

FIG. 3 shows a method for dynamically assigning wireless channels topriority groups and access points according to one embodiment;

FIG. 4 shows a set of access points installed in a building according toone embodiment;

FIG. 5A shows a first set of access point neighborhoods according toanother embodiment;

FIG. 5B shows a second set of access point neighborhoods according toanother embodiment;

FIG. 6A shows a client device in a first position in relation to a setof access points according to one embodiment;

FIG. 6B shows the client device in a second position in relation to aset of access points according to another embodiment; and

FIG. 6C shows the client device in a third position in relation to a setof access points according to another embodiment.

DETAILED DESCRIPTION

In the following description, for the purposes of explanation, numerousspecific details are set forth in order to provide a thoroughunderstanding. One or more embodiments may be practiced without thesespecific details. Features described in one embodiment may be combinedwith features described in a different embodiment. In some examples,well-known structures and devices are described with reference to ablock diagram form in order to avoid unnecessarily obscuring the presentinvention.

Herein, certain terminology is used to describe features for embodimentsof the disclosure. For example, the term “digital device” generallyrefers to any hardware device that includes processing circuitry runningat least one process adapted to control the flow of traffic into thedevice. Examples of digital devices include a computer, a tablet, alaptop, a desktop, a netbook, a server, a web server, an authenticationserver, an authentication-authorization-accounting (AAA) server, aDomain Name System (DNS) server, a Dynamic Host Configuration Protocol(DHCP) server, an Internet Protocol (IP) server, a Virtual PrivateNetwork (VPN) server, a network policy server, a mainframe, atelevision, a content receiver, a set-top box, a video gaming console, atelevision peripheral, a printer, a mobile handset, a smartphone, apersonal digital assistant “PDA”, a wireless receiver and/ortransmitter, an access point, a base station, a communication managementdevice, a router, a switch, and/or a controller.

It is contemplated that a digital device may include hardware logic suchas one or more of the following: (i) processing circuitry; (ii) one ormore communication interfaces such as a radio (e.g., component thathandles the wireless data transmission/reception) and/or a physicalconnector to support wired connectivity; and/or (iii) a non-transitorycomputer-readable storage medium (e.g., a programmable circuit; asemiconductor memory such as a volatile memory and/or random accessmemory “RAM,” or non-volatile memory such as read-only memory,power-backed RAM, flash memory, phase-change memory or the like; a harddisk drive; an optical disc drive; etc.) or any connector for receivinga portable memory device such as a Universal Serial Bus “USB” flashdrive, portable hard disk drive, or the like.

Herein, the terms “logic” (or “logic unit”) are generally defined ashardware and/or software. For example, as hardware, logic may include aprocessor (e.g., a microcontroller, a microprocessor, a CPU core, aprogrammable gate array, an application specific integrated circuit,etc.), semiconductor memory, combinatorial logic, or the like. Assoftware, logic may be one or more software modules, such as executablecode in the form of an executable application, an applicationprogramming interface (API), a subroutine, a function, a procedure, anobject method/implementation, an applet, a servlet, a routine, sourcecode, object code, a shared library/dynamic load library, or one or moreinstructions. These software modules may be stored in any type of asuitable non-transitory storage medium, or transitory computer-readabletransmission medium (e.g., electrical, optical, acoustical or other formof propagated signals such as carrier waves, infrared signals, ordigital signals).

Lastly, the terms “or” and “and/or” as used herein are to be interpretedas inclusive or meaning any one or any combination. Therefore, “A, B orC” or “A, B and/or C” mean “any of the following: A; B; C; A and B; Aand C; B and C; A, B and C.” An exception to this definition will occuronly when a combination of elements, functions, steps or acts are insome way inherently mutually exclusive.

Network System

FIG. 1 shows a block diagram example of a network system 100 inaccordance with one or more embodiments. The network system 100, asillustrated in FIG. 1, is a digital system that may include a pluralityof digital devices such as one or more access points 101 ₁-101 _(N), oneor more network controllers 103 ₁-103 _(M), and one or more clientdevices 105 ₁-105 _(P). The access points 101 ₁-101 _(N) and the networkcontrollers 103 ₁-103 _(M) may be connected through the switching fabric107 via wired and/or wireless connections. The client devices 105 ₁-105_(P) may be connected or otherwise associated with the access points 101₁-101 _(N) through corresponding wireless connections. As will bedescribed in greater detail below, each of the access points 101 ₁-101_(N) may be assigned wireless channels for communicating with otherdevices in the network system 100 (e.g., the client devices 105 ₁-105_(P)). In particular, wireless channels available for communication inthe network system 100 may be grouped based on priority. Thereafter,wireless channels from these groups may be assigned to access points 101₁-101 _(N) to ensure well-balanced, wide coverage, of stable channels inthe network system 100. Processes and techniques for grouping andassigning channels to access points 101 ₁-101 _(N) based on variousfactors will be described in greater detail below.

The network system 100 may be installed/distributed in any region orarea. For example, the network system 100 may be installed in an officebuilding or another similar structure. The location the network system100 is installed/distributed in defines a network environment. Thenetwork environment may be described by various characteristics,including size, location (e.g., country, state, county, city, etc.), andradio frequency (RF) characteristics of the area (e.g., RF interferenceor overlap with wireless channels of other systems).

Each element of the network system 100 will be described below by way ofexample. In one or more embodiments, the network system 100 may includemore or less devices than the devices illustrated in FIG. 1, which maybe connected to other devices within the network system 100 via wiredand/or wireless mediums. For example, in other embodiments, the networksystem 100 may include additional access points 101, network controllers103, and/or client devices 105 than those shown in FIG. 1.

The access points 101 ₁-101 _(N) may be any device that can associatewith the client devices 105 ₁-105 _(P) to transmit and receive data overwireless channels. Each of the access points 101 ₁-101 _(N) may operateon various wireless channels (i.e., frequency segments) that areassigned as described in greater detail below. In one embodiment, theaccess points 101 ₁-101 _(N) may correspond to a network device such asa wireless access point, a switch, a router, or any combination thereof.FIG. 2 shows a component diagram of the access point 101 ₁ according toone embodiment. In other embodiments, the access points 101 ₂-101 _(N)may include similar or identical components to those shown and describedin relation to the access point 101 ₁.

As shown in FIG. 2, the access point 101 ₁ may comprise one or more of:a hardware processor 201, data storage 203, an input/output (I/O)interface 205, and device configuration logic 207. Each of thesecomponents of the access point 101 ₁ will be described in further detailbelow.

The data storage 203 of the access point 101 ₁ may include a fastread-write memory for storing programs and data during performance ofoperations/tasks and a hierarchy of persistent memory, such as Read OnlyMemory (ROM), Erasable Programmable Read Only Memory (EPROM,) and/orFlash memory for example, for storing instructions and data needed forthe startup and/or operation of the access point 101 ₁. In oneembodiment, the data storage 203 is a distributed set of data storagecomponents. The data storage 203 may store data that is to betransmitted from the access point 101 ₁ or data that is received by theaccess point 101 ₁. For example, the data storage 203 of the accesspoint 101 ₁ may store data to be forwarded to the client devices 105₁-105 _(P) or to one or more of the network controllers 103 ₁-103 _(M).

In one embodiment, the I/O interface 205 corresponds to one or morecomponents used for communicating with other devices (e.g., the clientdevices 105 ₁-105 _(P), the network controllers 103 ₁-103 _(M), and/orother access points 101 ₂-101 _(N)) via wired or wireless signals. TheI/O interface 205 may include a wired network interface such as an IEEE802.3 Ethernet interface and/or a wireless interface such as an IEEE802.11 WiFi interface. The I/O interface 205 may communicate with theclient devices 105 ₁-105 _(P) and the network controllers 103 ₁-103 _(M)over corresponding wireless channels in the system 100. In oneembodiment, the I/O interface 205 facilitates communications between theaccess point 101 ₁ and one or more of the network controllers 103 ₁-103_(M) through the switching fabric 107. In one embodiment, the switchingfabric 107 includes a set of network components that facilitatecommunications between multiple devices. For example, the switchingfabric 107 may be composed of one or more switches, routers, hubs, etc.These network components that comprise the switching fabric 107 mayoperate using both wired and wireless mediums.

In some embodiments, the I/O interface 205 may include one or moreantennas 209 for communicating with the client devices 105 ₁-105 _(P),the network controllers 103 ₁-103 _(M), and/or other wireless devices inthe network system 100. For example, multiple antennas 209 may be usedfor forming transmission beams to one or more of the client devices 105₁-105 _(P) or the network controllers 103 ₁-103 _(M) through adjustmentof gain and phase values for corresponding antenna 209 transmissions.The generated beams may avoid objects and create an unobstructed path tothe client devices 105 ₁-105 _(P) and/or the network controllers 103₁-103 _(M).

In some embodiments, the access point 101 ₁ may include multiple radiosfor performing wireless transmissions. In these embodiments, each radioin the access point 101 ₁ may be assigned a separate wireless channel aswill be described in greater detail below.

In one embodiment, the hardware processor 201 is coupled to the datastorage 203 and the I/O interface 205. The hardware processor 201 may beany processing device including, but not limited to a MIPS/ARM-classprocessor, a microprocessor, a digital signal processor, an applicationspecific integrated circuit, a microcontroller, a state machine, or anytype of programmable logic array.

In one embodiment, the device configuration logic 207 includes one ormore functional units implemented using firmware, hardware, software, ora combination thereof for configuring parameters associated with theaccess point 101 ₁. In one embodiment, the device configuration logic207 may be configured to allow the access point 101 ₁ to associate withdifferent client devices 105 ₁-105 _(P).

As described above, the other access points 101 ₂-101 _(N) may besimilarly configured as described above in relation to access point 101₁. For example, the access points 101 ₂-101 _(N) may each comprise ahardware processor 201, data storage 203, an input/output (I/O)interface 205, and device configuration logic 207 in a similar fashionas described above in relation to the access point 101 ₁.

In one embodiment, the client devices 105 ₁-105 _(P) may be any wirelessor wired electronic devices capable of receiving and transmitting dataover wired and wireless mediums. For example, the client devices 105₁-105 _(P) may be one or more of personal computers, laptop computers,netbook computers, wireless music players, portable telephonecommunication devices, smart phones, tablets, and digital televisions.In one embodiment, the client devices 105 ₁-105 _(P) are digital devicesthat include a hardware processor, memory hierarchy, and input/output(I/O) interfaces including a wired and/or wireless interface such as anIEEE 802.3 interface. In one embodiment, the configuration of thecomponents within the client devices 105 ₁-105 _(P) may be similar tothose discussed above in relation to the access point 101 ₁. In otherembodiments, the client devices 105 ₁-105 _(P) may include more or lesscomponents than those shown in FIG. 2 in relation to the access point101 ₁.

The client devices 105 ₁-105 _(P) may be configured to operate on a setof frequency channels. For example, one or more of the client devices105 ₁-105 _(P) may be equipped/configured to operate on DynamicFrequency Selection (DFS) channels while other client devices 105 ₁-105_(P) are unable to operate on these DFS channels. Accordingly, thenetwork system 100 must be configured to assign wireless channels toaccess points 101 ₁-101 _(N) to ensure balanced coverage throughout thenetwork system 100 for client devices 105 ₁-105 _(P) of each type, tominimize effects of wireless interference in the network system 100 orwireless channel overlap with other higher priority systems, to increasefault tolerance in the network system 100, and/or to generally improvethe coverage and quality of connections in the network system 100.

In one embodiment, the network controllers 103 ₁-103 _(M) are digitaldevices that include a hardware processor, memory hierarchy, andinput/output (I/O) interfaces including a wired and/or wirelessinterface such as an IEEE 802.3 interface. In one embodiment, theconfiguration of the components within the network controllers 103 ₁-103_(M) may be similar to those discussed above in relation to the accesspoint 101 ₁. In other embodiments, the network controllers 103 ₁-103_(M) may include more or less components than those shown in FIG. 2 inrelation to the access point 101 ₁.

In one embodiment, the network controllers 103 ₁-103 _(M) may be any setof devices that assist the access points 101 ₁-101 _(N) in performingnetwork tasks and operations. For example, the network controllers 103₁-103 _(M) may assist in grouping and assigning wireless channels toaccess points 101 ₁-101 _(N) in the network system 100. Grouping andassignment of wireless channels may be performed based on variouscharacteristics and/or factors. For example, the characteristics and/orfactors may include client device 105 ₁-105 _(P) capabilities (e.g.,support for DFS channels), interference susceptibility, overlap ofchannels with other wireless systems operating on the samechannels/frequencies (e.g., DFS channels may operate on the samefrequencies as Radio Detection and Ranging (RADAR)), and channelregulatory requirements (e.g., equivalent isotropically radiated power(EIRP) regulatory requirements). The different processes and techniquesfor dynamically grouping and assigning wireless channels to accesspoints 101 ₁-101 _(N) will be discussed in greater detail below.

Although discussed above in relation to assignment of wireless channelsto access points 101 ₁-101 _(N), in some embodiments one or more of theaccess points 101 ₁-101 _(N) may include multiple radios that mayoperate on separate wireless channels (i.e., operate on separatefrequencies). In these embodiments, each radio in each of the accesspoints 101 ₁-101 _(N) may be assigned a separate wireless channel. Insome embodiments, channel grouping and/or assignment may take intoaccount that multiple radios are included in a single access point 101₁-101 _(N). For example, a process for assigning channels toradios/access points 101 ₁-101 _(N) may avoid assignment of multiple lowpriority or multiple high priority wireless channels to radios withinthe same access point 101 ₁-101 _(N). In this fashion, wireless channeldiversity based on priority level may be improved for areas surroundingeach access point 101 ₁-101 _(N).

Grouping and Assigning Wireless Channels to Access Points 101 ₁-101 _(N)

FIG. 3 shows a method 300 for dynamically grouping and assigningwireless channels to access points 101 ₁-101 _(N) according to oneembodiment. The method 300 may be performed by one or more devices inthe network system 100. For example, the method 300 may be performed byone or more of the network controllers 103 ₁-103 _(M) in conjunctionwith one or more of the access points 101 ₁-101 _(N). In one embodiment,one of the network controllers 103 ₁-103 _(M) may be designated as amaster network controller in the network system 100 such that eachoperation of the method 300 is performed by this designated masternetwork controller. In another embodiment, the method 300 may beentirely performed by one or more access points 101 ₁-101 _(N).

Although each of the operations in the method 300 are shown anddescribed in a particular order, in other embodiments, the operations ofthe method 300 may be performed in a different order. For example,although the operations of the method 300 are shown as being performedsequentially, in other embodiments the operations of the method 300 maybe performed concurrently or during partially overlapping time periods.

In the description of the method 300 that follows it is assumed thateach access point 101 ₁-101 _(N) includes a single radio. In thisscenario, assignment of wireless channels to access points 101 ₁-101_(N) is understood to be in relation to each radio within these accesspoints 101 ₁-101 _(N). In other embodiments, the method 300 may besimilarly applied to access points 101 ₁-101 _(N) with multiple radiossuch that each radio in each access point 101 ₁-101 _(N) is individuallyanalyzed for assignment of a corresponding wireless channel.

In one embodiment, the method 300 may commence at operation 301with thedetermining of the layout of the access points 101 ₁-101 _(N) in thenetwork environment in which the network system 100 is installed. Forexample, the network system 100, including the access points 101 ₁-101_(N), may be installed in an office building or another structure. FIG.4 shows an example set of access points 101 ₁-101 ₂₀ installed in anoffice building 400. In this embodiment, the office building 400 definesthe network environment in which the access points 101 ₁-101 ₂₀ areinstalled.

In one embodiment, operation 301 may determine the layout of the accesspoints 101 ₁-101 _(N) in the network environment based on signalstrength values from wireless signals transmitted and detected by theaccess points 101 ₁-101 _(N). For example, the access points 101 ₁-101_(N) may each emit a set of wireless signals in the network environment.These wireless signals may be for the purpose of transmitting databetween the corresponding access points 101 ₁-101 _(N) and anotherdevice and unrelated to the determination of access point 101 ₁-101 _(N)layout (e.g., application data and/or control signals transmitted overan established connection between an access point 101 ₁-101 _(N) andanother wireless device) or the wireless signals may be emitted for thepurpose of determining access point 101 ₁-101 _(N) layout. Upondetection of these wireless signals, an access point 101 ₁-101 _(N) maydetermine a power level of the received signal. Together with a knowntransmission power of the wireless signals, the signal strength valuesmay be used to determine the distance separating the access points 101₁-101 _(N) and direction of each access point 101 ₁-101 _(N) relative toeach other in the network environment. In one embodiment, the signalstrength indicators corresponding to these wireless signals may bereceived signal strength indicator (RSSI) values.

In another embodiment, the layout of the access points 101 ₁-101 _(N)may be determined based on a pre-populated access point 101 ₁-101 _(N)configuration table or another data structure, which describes thephysical layout of the access points 101 ₁-101 _(N) in the networkenvironment. For example, a system administrator may populate a tablewith a set of distance values and angle measurements describing thearrangement of the access points 101 ₁-101 _(N) in the networkenvironment. This access point 101 ₁-101 _(N) layout table may have beenpopulated during installation of the access points 101 ₁-101 _(N) in thenetwork environment.

As noted above, determination of the layout of the access points 101₁-101 _(N) may include the angle/direction and distance between theaccess points 101 ₁-101 _(N). In one embodiment, this information may beused to determine neighbor relationships between access points 101 ₁-101_(N). Two access points 101 ₁-101 _(N) may share a neighbor relationshipwhen there is a direct line of sight between the two access points 101₁-101 _(N) without any intermediary access points 101 ₁-101 _(N) betweenthe two neighboring access points 101 ₁-101 _(N). For example, in FIG.4, the access points 101 ₁ and 101 ₂ share a neighboring relationship.Similarly, the access points 101 ₂ and 101 ₃ share a neighboringrelationship. As noted above, this neighbor relationship between accesspoints maybe determined by distance and/or angle measurements while inother embodiments a pre-populated table may explicitly define neighborsfor each access point 101 ₁-101 _(N).

In one embodiment, neighborhoods of access points 101 ₁-101 _(N) may bedesignated based on continuous sets of neighboring access points 101₁-101 _(N). For example, FIG. 5A shows a set of neighborhoods, which aredesignated by dashed boxes. FIG. 5B shows a separate set ofneighborhoods for the same set of access points 101 ₁-101 _(N).Accordingly, neighborhoods may be variably defined within a networksystem 100. These neighborhoods may be used as a basis for channelassignment as will be described in greater detail below. In oneembodiment, neighborhoods may be defined in a pre-populated table.

In one embodiment, layout information determined at operation 301 mayalso be used to determine edge access points 101 ₁-101 _(N). Edge accesspoints 101 ₁-101 _(N) are access points 101 ₁-101 _(N) that lie on theoutside boundaries of the network environment. For example, in FIG. 4the access points 101 ₁-101 ₆, 101 ₁₀, 101 ₁₁, and 101 ₁₅-101 ₂₀ may beconsidered edge access points 101 ₁-101 _(N) based on their locationaround the periphery of the network environment in contrast to theaccess points 101 ₇-101 ₉ and 101 ₁₂-101 ₁₄, which are nested within theperimeter created by the edge access points 101 ₁-101 ₆, 101 ₁₀, 101 ₁₁,and 101 ₁₅-101 ₂₀.

At operation 303, characteristics of the network environment may bedetermined. The characteristics of the network environment may includedetection of the presence of radio-frequency (RF) interference orwireless channel overlap with other higher priority systems. Forexample, microwave interference (i.e., electromagnetic interference atapproximately 2.4 GHz) may be detected within the network environment.The microwave interference may be caused by one or more of a telephone,a baby monitor, a Bluetooth device, a car alarm, a microwave oven, andother devices that operate at or around 2.4 GHz or emit radio waves ator around 2.4 GHz. This microwave interference may affect certainwireless channels more than other channels. For example, IEEE802.11b/g/n may operate between 2.412 GHz and 2.484 GHz with 16.25 MHzto 22 MHz of channel separation. In this situation, microwaveinterference may affect particular wireless channels (i.e., frequencyranges) more severely than other wireless channels. Accordingly,operation 303 may indicate the range of wireless channels and/orfrequency ranges that are affected by detected microwave interference inthe network environment.

In one embodiment, operation 303 may detect signals from RADAR systemsand/or military systems operating or generating wireless signals around5 GHz. For example, operation 303 may detect wireless signals from othersystems in the 5.250 GHz-5.350 GHz and 5.470 GHz-5.725 GHz spectrums.Wireless signals in these frequency ranges may be the product of RADAR(e.g., Terminal Doppler Weather RADAR (TDWR) systems) and/or militarysystems. Additionally, wireless signals from RADAR and military systemsmay affect certain wireless channels more than other channels.Accordingly, operation 303 may indicate the range of wireless channelsand/or frequency ranges that are affected by detected RADAR and militarysystem wireless signals in the network environment (i.e., wirelesschannels used by RADAR and military system).

Although described in relation to wireless signals from RADAR andmilitary systems, in other embodiments wireless signals that overlapwith frequencies used by the network system 100 may be generated byother sources that are detected at operation 303. Accordingly, thedescription above is purely for illustrative purposes and in otherembodiments operation 303 may detect all forms of other wireless signalsactive in the network environment, which may affect wireless channelperformance.

At operation 305 the capabilities of the client devices 105 ₁-105 _(P)may be determined. In one embodiment, the capabilities may be relativeto currently associated client devices 105 ₁-105 _(P) in the networksystem 100 while in other embodiments capabilities may be determinedrelative to historical trends or analysis of client devices 105 ₁-105_(P) associated with access points 101 ₁-101 _(N) in the network system100.

In one embodiment, the capabilities of the client devices 105 ₁-105 _(P)may include the ability to support Dynamic Frequency Selection (DFS)channels. DFS is the process of detecting RADAR signals, which, based ongovernment regulations, must be protected against 5.0 GHz interference(e.g., IEEE 802.11a/n/ac radios). Upon detection of 5.0 GHzinterference, DFS causes access points 101 ₁-101 _(N) to switch theoperating frequency of the 5.0 GHz radio to a channel that is not beingused by the nearby RADAR or military systems. Transmission Power Control(TPC) may also be used to adapt the transmission power of a radio basedon regulatory requirements and range information to further avoid thisoverlapping with frequencies used with RADAR or military systems.

Originally, the 5 GHz band had a total of nine 20 MHz non-DFS channelsin the United States (i.e., channels that do not overlap withfrequencies being used by RADAR and/or military systems). However, afterthe introduction of 40 MHz channels in IEEE 802.11n and 80 MHz in IEEE802.11ac, the number of available non-DFS channels has reducedsignificantly. Currently, only four 40 MHz non-DFS channels or two 80MHZ channels are present in these standards. These newly availablewidths cause non-DFS channels to be crowded. This is especially evidentin highly dense network environments. In order to solve this densityissue, network administrators either attempted to disable 40 MHz and 80Mhz channels or began to utilize DFS channels. However, each of thesesolutions may pose issues.

In particular, when 40 MHz and 80 Mhz channels are disabled, clientdevices 105 ₁-105 _(P) may not enjoy the high speed experience providedby these channel widths. Further, if DFS channels are exclusively orsignificantly used, client devices 105 ₁-105 _(P) that do not supportDFS channels may suffer. Namely, if all access points 101 ₁-101 _(N)proximate to a DFS incapable client device 105 ₁-105 _(P) are on DFSchannels, this DFS incapable client device 105 ₁-105 _(P) will eithernot see a SSID or connect to a faraway access point 101 ₁-101 _(N) on anon-DFS channel. Connecting to a faraway access point 101 ₁-101 _(N) mayresult in the client device 105 ₁-105 _(P) experiencing latency issuesor a generally poor user experience. To better address these issues, themethod 300 may intelligently distribute/assign wireless channels toaccess points 101 ₁-101 _(N) in the network environment such thatbalanced coverage may be achieved for the capabilities of client devices105 ₁-105 _(P) represented in the network system 100. Techniques forchannel distribution will be described in greater detail below.

In some embodiments, other capabilities of the client devices 105 ₁-105_(P) may be determined at operation 305. For example, operation 305 maydetermine channels that are not supported by client devices 105 ₁-105_(P). Channel support may be based on current client devices 105 ₁-105_(P) in the network system 100, historic averages of client devices 105₁-105 _(P) associating with access points 101 ₁-101 _(N) within thenetwork system 100, and/or general client device 105 ₁-105 _(P) channelsupport.

At operation 307, regulatory requirements for the network environmentmay be determined. The regulatory requirements may include 1) DFSchannel restrictions and procedures for handling DFS channel assignment,2) equivalent isotropically radiated power (EIRP) regulatoryrequirements (i.e., regulations that indicate EIRP levels for particularchannels), and/or 3) the set of legally allowed wireless local areanetwork channels in the network environment (e.g., the availablechannels using IEEE 802.11 protocols). In one embodiment, theseregulatory requirements may be determined based on the location of thenetwork system 100 (e.g., the country, state, country, and/or city ofthe network system 100) and may be determined by querying a remoteregulatory server or by examining regulations previously stored inmemory (e.g., the data storage 203).

As noted above, one or more of the operations in the method 300 may beperformed in a different order than shown and described. For example,operations 301, 303, 305, and 307 may be performed in a different order,including during partially or fully overlapping time periods.

Following the determination of the layout of the access points 101 ₁-101_(N) at operation 301, the determination of characteristics of thenetwork environment at operation 303, the determination of thecapabilities of client devices 105 ₁-105 _(P) at operation 305, and thedetermination of the regulatory requirements of the network environmentat operation 307, operation 309 may assign each available wirelesschannel into groups. In one embodiment, these groups may indicate thepriority of associated wireless channels. For example, the channels 1-11corresponding to the 2.4 GHz spectrum and the channels 36, 40, 44, 48,52, 56, 60, 64, 100, 104, 108, 112, 116, 132, 136, 140, 149, 153, 157,161, and 165 corresponding to the 5 GHz spectrum may be available forassignment to access points 101 ₁-101 _(N). Table 1 below shows thecenter frequency of these channels.

TABLE 1 Channel Number Center Frequency (Hz) 1 2412 2 2417 3 2422 4 24275 2432 6 2437 7 2442 8 2447 9 2452 10 2457 11 2462 36 5180 40 5200 445220 48 5240 52 5260 56 5280 60 5300 64 5320 100 5500 104 5520 108 5540112 5560 116 5580 132 5660 136 5680 140 5700 149 5745 153 5765 157 5785161 5805 165 5825

The above channels are 20 MHz wide channels; however, in otherembodiments other channels and/or frequencies may be used (e.g., 40 MHzor 80 MHz). In this example set of channels shown above, each channelmay be assigned to priority groups based on characteristics of thechannels, characteristics of the network environment, and/or regulatoryrequirements for the network environment. For example, channels that areespecially prone to RF interference caused by nearby devices may beassigned to a lower priority group. RF interference may be microwaveinterference (e.g., caused by one or more of a telephone, a babymonitor, a Bluetooth device, a car alarm, a microwave oven, and otherdevices that operate at 2.4 GHz or emitting radio waves at 2.4 GHz). Inother embodiments, channels that overlap with frequencies being used byhigher priority systems may cause assignment of a lower priority tothese channels (e.g., DFS channels operating on RADAR/military systemfrequencies).

In one embodiment, the determination of channels that are prone tointerference may be determined based on the characteristics of thenetwork environment, which was determined at operation 303. In thisembodiment, the RF characteristics of the network environment may beexamined to determine particular frequency ranges for which RFinterference is present. Upon the detection of interference in thefrequency range of a particular set of channels, these channels may beassigned to a low priority group. For example, upon detecting RFinterference in the network environment in the range of 2412 Hz-2427 Hz,operation 309 may determine that channels 1-4 corresponding to thisfrequency range in Table 1 will be affected. Accordingly, operation 309may assign the channels 1-4 to a low priority group since these channelsmay be prone to RF interference in the current network environment.

In another example, the network environment characteristics determinedat operation 303 may include a detection of RADAR signals. In thisembodiment, DFS channels may be affected by these RADAR signals. Uponthe detection of RADAR signals, operation 309 may assign one or more DFSchannels to low priority groups. In one embodiment, only DFS channels infrequency ranges in which RADAR signals are detected may be assigned tolow priority groups.

Although described as assignment of channels to groups based on currentRF conditions in the network environment, in one embodiment assignmentof channels may be based on typical and/or historic conditions. Forexample, channels that have historically experienced interference in thenetwork environment and/or in other network environments may be assignedto low priority groups.

Operation 309 may also assign channels to groups based on low support bythe client devices 105 ₁-105 _(P). For example, operation 305 maydetermine that one or more of the client devices 105 ₁-105 _(P) may notsupport DFS channels. Accordingly, DFS channels may be moved to lowerpriority groups based on the level of support by the client devices 105₁-105 _(P). Conversely, high support for particular channels may causethese popular channels to be assigned to higher priority groups.

In some embodiments, assignment of channels to priority groups may beperformed to ensure some coverage for these types of channels in higherpriority groups. For example, in some embodiments, upon determining thatonly a few client devices 105 ₁-105 _(P) support DFS channels, acorresponding few DFS channels may be assigned to higher prioritychannel groups and each remaining DFS channel may be assigned to lowerpriority groups. Accordingly, DFS channels may ensure some coverage inthe network system 100 without over representation of these lowsupported channels.

Although described in relation to support of the client devices 105₁-105 _(P) currently operating within the network system 100, in someembodiments typical and/or historic support for channels may be used forchannel assignment. For example, channels that are historicallysupported by most wireless devices may be assigned to higher prioritygroups while channels that are historically supported by only a smallnumber of wireless devices may be assigned to lower priority groups.This historic analysis may be in relation to the current network system100 and/or other network systems.

In one embodiment, channels may be assigned to groups at operation 309based on high or low equivalent isotropically radiated power (EIRP)regulatory levels. For example, particular channels may be regulated bycountry, state, county, or city ordinances that restrict power levelsfor these channels above a particular amount. Channels that have EIRPlevels that are below a particular threshold may be assigned to a lowerpriority group at operation 309. In contrast, channels that have EIRPlevels that are above a particular threshold may be assigned to a higherpriority group at operation 309.

In one embodiment, the grouping of channels may be stored in a table oranother data structure at operation 309. For example, Table 2 includes afield/column indicating the group assigned to each wireless channel. Inthis example, four groups of decreasing priority are listed (i.e., group1 has a higher priority than group 2).

TABLE 2 Channel Number Center Frequency (Hz) Priority Group (1-4) 1 24124 2 2417 4 3 2422 4 4 2427 4 5 2432 1 6 2437 1 7 2442 1 8 2447 2 9 24522 10 2457 1 11 2462 1 36 5180 1 40 5200 1 44 5220 2 48 5240 2 52 5260 256 5280 2 60 5300 2 64 5320 2 100 5500 3 104 5520 3 108 5540 3 112 55603 116 5580 3 132 5660 3 136 5680 3 140 5700 3 149 5745 1 153 5765 1 1575785 1 161 5805 1 165 5825 1

Although factors and criteria for assigning channels to groups have beendescribed individually above, in some embodiments two or more sets offactors and criteria may be used for assigning wireless channels topriority groups. For example, the presence/absence of interference inthe frequency range of a channel along with the capability of the clientdevices 105 ₁-105 _(P) to support the channel may be used for wirelesschannel priority group assignment at operation 309.

In some embodiments, special conditions may be made to ensure particularchannels are represented in higher or lower priority groups. Forexample, in some embodiments a special condition may be established toensure that at least one or more DFS channels are placed in a higherpriority group. This assignment may be made to ensure are least oneaccess point 10!₁-101 _(N) is assigned a DFS channel in a laterassignment operation.

Following assignment of the channels to priority groups, operation 311may assign channels from the priority groups to access points 101 ₁-101_(N). The techniques for assigning channels to access points 101 ₁-101_(N) may be based on various factors and criteria. Several exampletechniques will be described in detail below. However, in otherembodiments, other techniques may be used in addition to those describedbelow for assigning wireless channels to access points 101 ₁-101 _(N).

In the description of operation 311 that follows it is assumed that eachaccess point 101 ₁-101 _(N) includes a single radio. In this scenario,assignment of wireless channels to access points 101 ₁-101 _(N) isunderstood to be in relation to each radio within these access points101 ₁-101 _(N). In other embodiments, operation 311 may be similarlyapplied to access points 101 ₁-101 _(N) with multiple radios such thateach radio in each access point 101 ₁-101 _(N) is individually analyzedfor assignment of a corresponding wireless channel.

In one embodiment, operation 311 may assign channels from prioritygroups to ensure efficient channel distribution among neighboring accesspoints 101 ₁-101 _(N). In this embodiment, the layout of the accesspoints 101 ₁-101 _(N), including the neighboring relationships betweenaccess points 101 ₁-101 _(N) determined at operation 301, may be used toassign wireless channels. For example, sets of neighboring access points101 ₁-101 _(N) may be examined as a neighborhood as shown in FIG. 5A andFIG. 5B. In this example, no neighborhood may have a higherconcentration of channels from low priority groups and/or or a higherconcentration of channels from high priority groups than any otherneighborhoods. For instance, using the priority groups in Table 2 andthe neighborhoods in FIG. 5A, if the access points 101 ₁, 101 ₂, 101 ₆,and 101 ₇ define a first neighborhood and the access points 101 ₃-101 ₅and 101 ₈-101 ₁₀ define a second neighborhood, operation 311 may assignan equal number of channels from the high priority groups 1 and 2 toboth the access points 101 ₁, 101 ₂, 101 ₆, and 101 ₇ in the firstneighborhood and the access points 101 ₃-101 ₅ and 101 ₈-101 ₁₀ in thesecond neighborhood. Similarly, operation 311 may assign an equal numberof channels from the low priority groups 3 and 4 to both the accesspoints 101 ₁, 101 ₂, 101 ₆, and 101 ₇ in the first neighborhood and theaccess points 101 ₃-101 ₅ and 101 ₈-101 ₁₀ in the second neighborhood.In this example, assignment from lower priority groups may only beperformed after channels from higher priority groups have beenexhausted. In some embodiments, the number of channels in each groupfrom each neighborhood does not need to be equal, but instead must bewithin some difference threshold in comparison to other groups.

In one embodiment, operation 311 may assign channels from prioritygroups to ensure balanced coverage of high priority channels throughoutthe network environment. In this embodiment, high priority channels areassigned to access points 101 ₁-101 _(N) such that at least one highpriority channel is available to most if not all locations in thenetwork environment. For example, operation 311 may examine the layoutof access points 101 ₁-101 _(N) determined at operation 301 to establishthe expected coverage area of each of these access points 101 ₁-101_(N). Upon establishing coverage areas of each access point 101 ₁-101_(N), including overlapping wireless coverage, operation 311 maydetermine a distribution of wireless channels from the priority group 1and/or the priority group 2 (e.g., the high priority channel groups)such that the percentage of area covered by high priority channels ismaximized. After distribution of high priority channels, remainingaccess points 101 ₁-101 _(N) may be assigned a wireless channel from theremaining lower priority groups (e.g., groups 3 and 4).

As noted above, in some embodiments one or more of the access points 101₁-101 _(N) may include multiple radios that may operate on separatewireless channels (i.e., operate on separate frequencies). In theseembodiments, each radio in each of the access points 101 ₁-101 _(N) maybe assigned a separate wireless channel. In some embodiments, channelassignment may take into account that multiple radios are included in asingle access point 101 ₁-101 _(N). For example, operation 311 may avoidassignment of multiple low priority or multiple high priority wirelesschannels to radios within the same access point 101 ₁-101 _(N). In thisfashion, wireless channel diversity based on priority level may beimproved for areas surrounding each access point 101 ₁-101 _(N).

Although described above as assigning both channels from high priorityand low priority groups, in some embodiments channels from low prioritygroups may only be assigned when channels from higher priority groupsfail to meet one or more criteria. For example, one or more channelsfrom a low priority group may be necessary to meet a performancethreshold, provide network availability for each client device 105 ₁-105_(P), a minimum throughput threshold, a maximum bandwidth threshold, amaximum congestion level, etc.

In one embodiment, operation 311 may assign channels from prioritygroups to ensure increased fault tolerance in the network system 100. Inthis embodiment, channels in lower priority groups may be surrounded bychannels from higher priority groups. For example, the access points 101₁₋ 101 ₃, 101 ₆, 101 ₈, 101 ₁₁, 101 ₁₃, and 101 ₁₆-101 ₁₈ in FIG. 4 maybe assigned channels from the groups 1 and 2 while access points 101 ₇and 101 ₁₂ may be assigned channels from the groups 3 and 4. In thisfashion, the access points 101 ₁₋ 101 ₃, 101 ₆, 101 ₈, 101 ₁₁, 101 ₁₃,and 101 ₁₆-101 ₁₈ with high priority channels may surround the accesspoints 101 ₇ and 101 ₁₂ with low priority channels. By surrounding lowpriority channels with high priority channels, operation 311 may ensurethat any faults or quality issues that may occur on low prioritychannels (e.g., the channels in the groups 3 and 4) may be overcome bynearby high priority channels. As noted above in relation to operation309, these high priority channels are less likely affected byinterference or other problems that may cause deterioration in thequality of coverage. Further, these high priority channels may be highlycompatible with more client devices 105 ₁-105 _(P). However, by stillallowing lower priority channels to be assigned to access points 101₁-101 _(N) the method 300 ensures wide support for many different typesof client devices 105 ₁-105 _(P).

In one embodiment, channel assignment at operation 311 may be performedbased on the location of the access points 101 ₁-101 _(N) in the networkenvironment. In this embodiment, the layout of the access points 101₁-101 _(N) determined at operation 301 may be used for assigningchannels. For example, channels in higher priority groups may beassigned to edge access points 101 ₁-101 _(N), while non-edge accesspoints 101 ₁-101 _(N) may be assigned channels from low priority groups.For instance, the access points 101 ₁-101 ₆, 101 ₁₀, 101 ₁₁, and 101₁₅-101 ₂₀ in FIG. 4 may be considered edge access points 101 ₁-101 _(N)based on their location around the periphery of the network environmentin contrast to the access points 101 ₇-101 ₉ and 101 ₁₂-101 ₁₄ which arenested within the perimeter created by the edge access points 101 ₁-101₆, 101 ₁₀, 101 ₁₁, and 101 ₁₅-101 ₂₀. These edge access points 101 ₁-101₆, 101 ₁₀, 101 ₁₁, and 101 ₁₆-101 ₂₉ may be assigned wireless channelfrom high priority groups while the non-edge access points 101 ₇-101 ₉and 101 ₁₂-101 ₁₄ may be assigned wireless channels from low prioritygroups. As noted above, channels in low priority groups may be moresusceptible to interference or frequency overlap from externals sources.By nesting low priority channels, which are sensitive to interference,inside the network environment, low priority channels are less likely tobe affected by interference since these access points 101 ₇-101 ₉ and101 ₁₂-101 ₁₄ are more distant from possible sources of interference.

Although the example techniques provided above are discussedindividually, in some embodiments multiple techniques and/or factors maybe used at operation 311 for assignment of channels to access points 101₁-101 _(N). For example, in some embodiments channel assignment toaccess points 101 ₁-101 _(N) may ensure both balanced distribution ofchannels from each group and increased fault tolerance based on thelocations of the access points 101 ₁-101 _(N). For example, FIG. 6Ashows a set of access points 101 ₁-101 ₆ and a client device 105 ₁. Inthis example, the client device 105 ₁ may be DFS incapable. In thissituation, operation 311 may ensure that edge access points 101 ₁ and101 ₆ do not use DFS channels. This prevents the situation where theclient device 105 ₁ is in a corner location, as shown in FIG. 6B, andthe closest available access point 101 ₁-101 ₆ is the access point 101₅. Since the access point 101 ₅ may be relatively far from the clientdevice 105 ₁, connection quality issues may be a problem for the clientdevice 105 ₁. Further, operation 311 may ensure that neighboring accesspoints 101 ₁-101 _(N) are not both on DFS channels. For example, if bothaccess points 101 ₂ and 101 ₃ are on DFS channels and both the accesspoints 101 ₁ and 101 ₄ are on non-DFS channels and the client device 105₁ is situated as shown in FIG. 6C, the client device 105 ₁ will attemptto associate with one of the access points 101 ₁and 101 ₄, which isconsiderably farther away from the client device 105 ₁ in comparison tothe access points 101 ₂ and 101 ₃. Accordingly, even though an evennumber of access points 101 ₁-101 _(N) may be assigned high/low prioritychannels (e.g., non-DFS and DFS channels) in a particular neighborhood,assigning neighboring access points 101 ₁-101 _(N) to either high or lowpriority channels (e.g., non-DFS or DFS channels) may create qualityissues (i.e., increased faults). Accordingly, in FIG. 6C the accesspoints 101 ₁-101 ₆ may be alternatively assigned DFS channels to ensurefull coverage for the client device 105 ₁ while roaming through thenetwork environment.

Further, in one embodiment, a client device 105 ₁ shown in FIG. 6C maybe associated with the access point 101 ₂. In this embodiment, theclient device 105 ₁ may not support any of the other channels on whichother proximate access points 101 ₁ 101 ₃ are operating. In thissituation, operation 311 should not alter the channel assignment for theaccess point 101 ₂ with which the client device 105 ₁ is associated asthis reassignment may cause the client device 105 ₁ to be unable toassociate with a proximate access point 101 ₁ or 101 ₃. In turn, thismay cause connectivity issues for the client devices 105 ₁-105 _(P).

In one embodiment, operation 313 may steer client devices 105 ₁-105 _(P)to less crowded access points 101 ₁-101 _(N). For example, access points101 ₁-101 _(N) may be assigned DFS and non-DFS channels at operation311. In some situations, since many client devices 105 ₁-105 _(P) maynot support DFS channels, the non-DFS channels/access points 101 ₁-101_(N) may become heavily crowded with both DFS capable client devices 105₁-105 _(P) and DFS incapable client devices 105 ₁-105 _(P). To alleviatethis overcrowding on non-DFS channels, operation 313 may steer DFScapable client devices 105 ₁-105 _(P) to access points 101 ₁-101 _(N)using DFS channels.

As described above, the method 300 may assign wireless channels topriority groups based on characteristics of the channels, theenvironment in which the channels will be used, regulatory requirements,and/or capabilities of the client devices 105 ₁-105 _(P). Thereafter,channels may be intelligently assigned to access points 101 ₁-101 _(N)to achieve one or more goals. For example, wireless channels may beassigned to access points 101 ₁-101 _(N) to ensure balanced coveragethroughout the network system 100 for client devices 105 ₁-105 _(P) ofeach type/capability, to minimize effects of wireless interference inthe network system 100, to increase fault tolerance in the networksystem 100, and/or to generally improve the coverage and quality ofconnections in the network system 100.

An embodiment of the invention may be an article of manufacture in whicha machine-readable medium (such as microelectronic memory) has storedthereon instructions which program one or more data processingcomponents (generically referred to here as a “processor”) to performthe operations described above. In other embodiments, some of theseoperations might be performed by specific hardware components thatcontain hardwired logic (e.g., dedicated digital filter blocks and statemachines). Those operations might alternatively be performed by anycombination of programmed data processing components and fixed hardwiredcircuit components. Also, although the discussion focuses on uplinkmedium control with respect to frame aggregation, it is contemplatedthat control of other types of messages is applicable.

Any combination of the above features and functionalities may be used inaccordance with one or more embodiments. In the foregoing specification,embodiments have been described with reference to numerous specificdetails that may vary from implementation to implementation. Thespecification and drawings are, accordingly, to be regarded in anillustrative rather than a restrictive sense. The sole and exclusiveindicator of the scope of the invention, and what is intended by theapplicants to be the scope of the invention, is the literal andequivalent scope of the set of claims that issue from this application,in the specific form in which such claims issue, including anysubsequent correction.

1-16. (canceled)
 17. A method comprising: assigning a first subset oftwo or more channels, of a plurality of channels, to a first group ofchannels of a first priority level based on a level of support of thechannels in the first subset by client devices; assigning a secondsubset of channels, of the plurality of channels, to a second group ofchannels of a second priority level different from the first prioritylevel based on a level of support of the channels in the second subsetby the client devices; determining that a first access point is locatedwithin a radio frequency range of a second access point; responsive todetermining that the first access point is located within the radiofrequency range of the second access point, configuring the first accesspoint to use one of the channels from the first group of channels of thefirst priority level and configuring the second access point to use oneof the channels from the second group of channels of the second prioritylevel.
 18. The method of claim 17, wherein the first group of channelscomprises Dynamic Frequency Selection (DFS) channels and wherein thesecond group of channels comprises non-DFS channels.
 19. The method ofclaim 17, wherein the first group of channels comprises channelsassociated with a first frequency of RADAR detections and the secondgroup of channels comprises channels associated with a second frequencyof RADAR detections different than the first frequency of RADARdetections.
 20. The method of claim 17, wherein assigning the firstsubset of channels to the first group of channels is responsive todetermining that each channel of the first subset of channels isassociated with the first priority level, and wherein assigning thesecond subset of channels to the second group of channels is responsiveto determining that each channel of the second subset of channels isassociated with the second priority level.
 21. The method of claim 17,further comprising: determining a number of devices to assign to thefirst group of channels based on a number of client devices associatedwith one or more characteristics of the first group of channels.
 22. Themethod of claim 17, further comprising: dynamically modifying a numberof channels assigned to the first group of channels based oncharacteristics associated with detected client devices.
 23. The methodof claim 17, wherein assigning the first subset of channels to the firstgroup of channels is responsive to determining that each channel of thefirst subset of channels is associated with a first equivalentisotropically radiated power (EIRP) range, and wherein assigning thesecond subset of channels to the second group of channels is responsiveto determining that each channel of the second subset of channels isassociated with a second EIRP range different than the first EIRP range.24. The method of claim 17, wherein assigning the first subset ofchannels to the first group of channels is responsive to determiningthat each channel of the first subset of channels is associated with afirst frequency of detected interference, and wherein assigning thesecond subset of channels to the second group of channels is responsiveto determining that each channel of the second subset of channels isassociated with a second frequency of detected interference differentthan the first frequency of detected interference.
 25. The method ofclaim 17, wherein assigning the first subset of channels to the firstgroup of channels is responsive to determining that each channel of thefirst subset of channels is statistically prone to a first level ofinterference, and wherein assigning the second subset of channels to thesecond group of channels is responsive to determining that each channelof the second subset of channels is statistically prone to a secondlevel of interference different than the first level of interference.26. The method of claim 17, wherein assigning the first subset ofchannels to the first group of channels is responsive to determiningthat each channel of the first subset of channels is associated with afirst level of fault tolerance, and wherein assigning the second subsetof channels to the second group of channels is responsive to determiningthat each channel of the second subset of channels is associated with asecond level of fault tolerance different than the first level of faulttolerance.
 27. The method of claim 17, wherein the operations furthercomprise configuring a plurality of access points for a plurality ofregions such that each region has at least one access point configuredto use a channel of the first group of channels.
 28. The method of claim17, wherein the operations further comprise configuring a plurality ofaccess points for a plurality of regions such that each region has atleast a threshold number of access points, the threshold number for eachregion being based on characteristics of that each region.
 29. A methodcomprising: determining that a first access point is located at an edgeof a Wi-Fi coverage area and a second access point is not located at theedge of the Wi-Fi coverage area; responsive to the determiningoperation: assigning the first access point a non-Dynamic FrequencySelection (DFS) channel belonged to a first group of channels of a firstpriority level; and assigning the second access point to a DFS channelbelonged to a second group of channels of a second priority leveldifferent from the first priority level.
 30. A method comprising:partitioning a plurality of channels into two or more subsets ofchannels of different priority levels based on characteristics of thechannels, characteristics of a network environment in which the channelsare used, and regulatory requirements for the network environment,wherein each subset of channels has two or more channels; prioritizingthe two or more subsets of channels based on the characteristics of thechannels and the network environment and the regulatory requirements;and configuring an access point to select a channel from the subsets ofchannels based on the prioritizing operation.
 31. The method of claim15, wherein configuring the access point comprises configuring theaccess point to use a channel in a low priority subset, of the pluralityof channels, only when all channels in a high priority subset of theplurality of channels does not meet one or more criteria.